Skip to content

[Performance] Optimize header sanitization guard#7621

Draft
gonzaloriestra wants to merge 2 commits into
mainfrom
performance-optimize-header-sanitization-12902459395274013251
Draft

[Performance] Optimize header sanitization guard#7621
gonzaloriestra wants to merge 2 commits into
mainfrom
performance-optimize-header-sanitization-12902459395274013251

Conversation

@gonzaloriestra
Copy link
Copy Markdown
Contributor

WHY are these changes introduced?

The sanitizedHeadersOutput function is called for every network request to prepare debug logs, even when debug logging is disabled. This results in unnecessary object iteration, string manipulation, and regex searches on every request.

WHAT is this pull request doing?

  • Adds an early return guard to sanitizedHeadersOutput that returns an empty string immediately if the CLI is not in verbose mode and not in a unit test.
  • Moves the sensitive keywords array to a module-level constant to avoid re-allocation on every call.

How to test your changes?

CI

Checklist

  • I've considered possible cross-platform impacts (Mac, Linux, Windows)
  • I've considered possible documentation changes
  • I've considered analytics changes to measure impact
  • The change is user-facing — I've identified the correct bump type (patch for bug fixes · minor for new features · major for breaking changes) and added a changeset with pnpm changeset add

PR created automatically by Jules for task 12902459395274013251 started by @gonzaloriestra

The `sanitizedHeadersOutput` function was identified as a bottleneck in network request logging because header sanitization logic executed even when debug logging was inactive. This change adds an early return guard that returns an empty string if verbose logging is not enabled and the CLI is not running in a unit test environment.

Additionally, the sensitive headers keyword array has been moved to a module-level constant to avoid repeated allocations.
@google-labs-jules
Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@github-actions github-actions Bot added the no-changelog This PR doesn't include a changeset entry. Is an internal only change not relevant to end users. label May 24, 2026
The `sanitizedHeadersOutput` function was identified as a bottleneck in network request logging because header sanitization logic executed even when debug logging was inactive. This change adds an early return guard that returns an empty string if verbose logging is not enabled and the CLI is not running in a unit test environment.

Additionally, the sensitive headers keyword array has been moved to a module-level constant to avoid repeated allocations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-changelog This PR doesn't include a changeset entry. Is an internal only change not relevant to end users.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant